home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
os2
/
gigo0714.zip
/
MAILLIST.CFG
< prev
next >
Wrap
Text File
|
1996-07-14
|
12KB
|
245 lines
; MAILING LISTS!
; GIGO will now internally support hosting of mailing lists.
; If you are not hosting the mailing list, but instead trying
; to _gate_ the mailing list, see the MAPPING.CFG file instead.
;
; Once again: This section is if you want to HOST a mailing list.
;
; ┌──────────────────────────────────────────────────────────────┐
; │ IF YOU WISH TO USE THE MAILING LIST FEATURES, YOU WILL │
; │ NEED TO MAKE SURE THAT THIS CONFIG FILE GETS INCLUDED IN YOUR│
; │ SETUP! │
; │ IE, ADD "Include MailList.Cfg" TO YOUR GATEWAY.CFG FILE! │
; └──────────────────────────────────────────────────────────────┘
;
; There are two keywords involved. CAPTURE is what will capture
; the messages from a given email address, echomail area, or newsgroup,
; and save them as .MLQ files in the directory you specify.
; EXPLODE will take the MLQ files, and send them out to a list of recipients.
;
; In addition, you will need to setup SITE statements for the purpose of
; giving the mailing list (which is email based) access to posting
; into the newsgroups and into the echos with.
;
SITE pnews news ; Any mail sent to news.group@pnews.yoursite.domain gets posted
SITE pecho echo ; Any mail sent to echoname@pecho.yoursite.domain gets posted
; When GIGO is sending out messages for your mailing list, it tries to bunch
; as many people as possible onto each message, thereby reducing how much outgoing
; traffic you actually create. By default, it is about 10 addresses per outgoing
; message, meaning that a mailing list with 50 recipients will generate about
; 5 outgoing messages (instead of 50!).
;
; Of couse, this parameter is tweekable :-)
;
; The MAXRMAIL command specifies the maximum line length for outgoing
; email to your host. If they are running unix, you can try increasing this
; up to 1024 or even 2048. If your host is running Waffle under DOS,
; drop this number down to 100. If you want to specify that only one
; person per message should be used, try "1".
MAXRMAIL 256
; The ML-COPY command tells GIGO to send back a copy of the mailing list
; message to the person who posts (if they are subscribed to the mailing
; list). By default, users who post are not sent back a copy
; of their message, since they've already seen the message. ;-).
;
;ML-COPY
; The ML-HEADERS command tells GIGO to import as many headers
; as reasonably possible into the mailing lists. This will bloat
; the header sizes, but will allow for mime posts to the mailing
; lists.
ML-HEADERS
; The ML-RECEIVED-HEADERS
; Some people may want to import Received: lines, to show the message
; paths before the messages reach your machine. Personally, I don't
; want'em..
;ML-RECEIVED-HEADERS
; ML-NEWSGROUPS tells GIGO that you want to keep the Newsgroups:
; kludge line, for cases where a mailing list is crossposted with
; a newsgroup.
; ML-NEWSGROUPS
;
; The two commands are seperated, so that I (or someone else) can easily
; add in the ability to create Digest Messages (where one email message
; contains several mailing list messages), and also so that anyone who
; wishes to archive the messages into a text file may do so.
;
;CAPTURE dirname\ inputaddress owner newsgroup ECHONAME badmail.ml Description
;EXPLODE dirname\ listfile.ml owner postnewsaddress postechoaddress
;
; PHASE 1 : CAPTURING MESSAGES FOR THE MAILING LIST
;
; CAPTURE dirname\ inputaddress owner newsgroup ECHONAME Description
; CAPTUREPRIV listname.ml dirname\ inputaddress owner newsgroup ECHONAME Description
;
; The CAPTURE statement is designed to capture the messages from various
; sources.
; o listname.ml : (CAPTUREPRIV only)
; The message will only be CAPTURE'd if the sender
; is on the mailing list. Otherwise, the CAPTUREPRIV
; statement is ignored. See samples.
; o dirname\ : You _must_ dedicate a single directory
; to each mailing list that you wish to support.
; o inputaddress: This is the address that people send messages
; to when they want their message sent to everyone else.
; o owner : The address where errors in mail delivery should
; go to, examples are listname-err or listname-owner.
; o newsgroup : The newsgroup to capture and deliver to for gating
; (if not porting to a newsgroup, use a single dash "-")
; o ECHONAME : The echoarea that you want to capture and deliver to
; for gating (if not porting to an echo, use a single dash)
; o badmail.ml : This is a text file describing which messages you
; do _not_ want redistributed. This would include
; provisions for watching for messages from mailer
; daemons and other message notification messages.
; A sample will be included in the GIGO archive.
; o Description : A small line of text, ie "Foobar-Baz Mailing List"
;
; When GIGO is running, if it gets any messages to the inputadddress,
; or in the newsgroup or echo specified, it will save that message in
; the dirname\ as a *.MLQ file (.Mailing List Queue). The first line
; of that text file should be a Ctrl-A immediately followed by
; the email address of the person submitting the message, or NEWS,
; or ECHO. This information, if present, will help GIGO not send a
; duplicate message back out to the source where the message came from.
; It will strip most headers off, only keeping the pertinant ones.
; It will also contain an "Errors-To:" address, with the address
; of owner in it.
;
; PHASE 2 : EXPLODING MESSAGES FROM THE MAILING LIST TO THE RECIPIENTS
;
; EXPLODE dirname\ listfile.ml owner postnewsaddress postechoaddress
;
; The EXPLODE statement is used to take the MLQ files, and to send it to
; a list of recipients.
;
; o dirname\ : You _must_ dedicate a single directory
; to each mailing list that you wish to support.
; o listfile.ml : This is an ascii list of recipients that wish
; to receive messages from this mailing list.
; This file should contain one address per line.
; You may either edit the file manually, or look into
; installing LISTSERV which can automate subscription
; requests for multiple mailing lists.
; o owner This is where errors should be sent to.
; Common: listname-owner or listname-err
; o postnewsaddress This is where messages that need to be posted
; to a newsgroup need to be sent. GIGO provides
; an email-to-news interface, which you will need
; to have setup for this purpose (should be done up above!)
; (If you do not wish to have messages posted to the
; newsgroup, specify a single dash "-").
; o postechoaddress This is where messages that need to be posted
; to a fidonet echo need to be sent. GIGO provides
; an email-to-echomail interface, which you will need
; to have setup for this purpose.
; (If you do not wish to have messages posted to the
; echo, specify a single dash "-").
;
;
; Whenever GIGO runs, if there are any EXPLODE statements in the config
; file, GIGO will look at the specified files for *.MLQ files. If
; it finds any, it will process those files, and rename them to
; *.MLS files (Mailing List Sent). You may either do further processing
; on them, or simply delete them - that is up to you. The author
; saves them in an archive for later use.
;
; When GIGO finds a MLQ file to be sent out, it will take a look at the
; first line of the file. If it starts with Ctrl-A (""), it will
; assume that that first line contains the phrase "NEWS", "ECHO",
; or th